feat: add scalable venue catalog queries #58
Merged
+298
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
venueswith optional server-side search, venue-type filtering, sorting and paginationvenueTypesso the client can build its filter options from database valuesSearch is case-insensitive across name, area and type. Multiple venue types are combined with OR. Rating sorting places unrated venues last and uses name and ID as stable tie-breakers. SQL values are parameterized, and literal wildcard characters in searches are escaped.
Verification
npm --prefix server run typechecknpm --prefix server run test:data— 60 tests passednpm --prefix server run buildgit diff --checkDeployment order
This backend change must be reviewed, merged and deployed to the VM before frontend PR #56 is merged. All new arguments are optional, so deploying the backend first remains compatible with the current frontend.